Your website has no major code errors
Parsing is the way software like web browsers and assistive technology read and understand a website. It’s important that the different technologies your users use to view your website don’t have trouble parsing your website. Parsing is all about your website’s code.
All your users will benefit from a website
‘Labels or Instructions’ requires forms and controls to provide labels or instructions for user input.
Introduction
Most websites have at least some elements that require user input. For example, these might be controls or forms. It’s essential to label controls such as radio buttons and checkboxes so that users understand what they are selecting.
It can also be
‘Error Identification’ requires websites to identify and describe input errors for users.
Introduction
Users of all kinds will make mistakes when using your website, so it’s important to clearly identify and describe errors. Input errors include users not providing required information as well as providing informating that doesn’t meet validation criteria.
Be as specific as possible when highlighting
Elements do not change when they receive input.
Introduction
As we saw with On Focus, all users need predictability when navigating a website. If elements don’t act as they expect, they may become disorientated.
This is also true when elements receive input, they shouldn’t automatically change. For example, forms shouldn’t skip to another field or auto-submit without confirmation
Elements do not change when they receive focus.
Introduction
All users need predictability when navigating a website. If elements doesn’t act as they expect, they may become disorientated.
In particular, once an element receives focus from a user, whether with a mouse or keyboard, the element must not automatically change (known as ‘changing on focus’). This can disorientate
‘Language of Page’ requires that each webpage has a default human language assigned.
Introduction
For both users who rely on conventional web browsers and those who prefer assistive technologies, assigned a webpage’s language is essential for understanding.
Among the benefits, text is rendered more accurately, screen readers will use the correct pronunciation rules and captions will load correctly.
How
‘Link Purpose (In Context)’ requires that every link’s purpose is clear from its text or context.
Introduction
It’s essential that you make your links clear and easy to understand, ideally from just the link text itself.That’s because users with assistive technology, like a screen reader, often hear all the links on a page to help them find
‘Enhancing web 2.0 accessibility via AxsJAX’ was a 2008 Google Tech Talk , presented by Charles Chen and T.V Raman. The video is a technical tutorial of AxsJAX, or Access-Enabling AJAX. AxsJAX was a Google project that injected web accessibility standards into web 2.0 properties – many of which rely on JavaScript.
This post is for
‘Focus Order’ requires that components receive focus in a logical sequence.
Introduction
Your users need to find their way around your website in a sequential and meaningful order. You can control this with the ‘focus order’ of your website.
This is the sequence in which users access components on your website. Users with keyboard-only navigation or screen readers
‘Page Titled’ means using helpful and clear… page titles.
Introduction
All users benefit from descriptive page titles. A good title tells your users which page they are on and what that page is for. This lets users quickly understand if they are on the right page.
Users with visual, cognitive and mobility impairments further benefit as the technology
