Accessibility is based upon a ratio off 60% Priority 1(A) and 40% Priority 2 (AA). ...
Accessibility is based upon a ratio off 60% Priority 1(A) and 40% Priority 2 (AA). This reflects the importance of Priority 1 over Priority 2.
eAccessibility Country Information is data gathered by the eInclusion@EU project and National Correspondents attached to the project. The contry information investigates the situation on various eAccessibility related issues for each country.
Coordinated action by EU Member States is needed to make information and communication technologies (ICTs) more accessible to all, and particularly to people with disabilities and some older persons, said the European Commission today. In a Communication on “Electronic Accessibility” (eAccessibility), adopted today, the Commission calls upon Member States to do more to promote EU e-Accessibility initiatives in a concerted approach and to encourage uptake by industry. Progress will be reviewed two years from now, when additional measures may be proposed, including new legislation if necessary.
The Commission has opted for a careful approach to integrating senior citizens and people with disabilities into the information society, favouring standardisation over regulation.
Tables are intended to display tabular data, their use to control layout should be discouraged ...
Tables are intended to display tabular data, their use to control layout should be discouraged but not ruled out. Instead the use of additional mark-up can ensure a page remains accessible to all.
Guideline 5 of WCAG 1.0 covers several recommendations under the banner "Create tables that transform gracefully":
Sitemorse will report a 'wcag10/linktarget' diagnostic when the same link text is used for different ...
Sitemorse will report a 'wcag10/linktarget' diagnostic when the same link text is used for different target URLs. An important aspect of link text is its uniqueness. Typically a web page may link to several resources, either directing the user to different parts of the same page, or to different pages altogether.
Each link to a different target must have a unique description text, allowing users to quickly, and unambiguously, locate content on a page.
Take, for instance, a page which links to company reports:
The link text in both cases is simply "report", the description is not unique.
To resolve this alter the link text to ensure uniqueness:
Alternatively Sitemorse also takes into account the 'title' attribute. Thus the following example is also permitted:
In this example the first solution is certainly desirable.
The option to include a set of tools to adjust the screen font sizes is ...
The option to include a set of tools to adjust the screen font sizes is not a requirement of the Web Content Accessibility Guidelines.
As ever, the basic principle is that all the content should be accessible to people who need to vary the font size. Therefore there are a couple of points to note:
There is no need to add a separate control to vary the font size on the web site. Users' browsers already have this control built-in to their web browser, which, if the rules above are followed, will work perfectly well with no assistance required from the web site itself.
Some people like to add such a feature regardless, perhaps as a "visible demonstration" of commitment to accessibility. break any rules.
All images must supply a text equivalent. The term "text equivalent" can be "nothing" - ...
All images must supply a text equivalent. The term "text equivalent" can be "nothing" - the simplest example being "spacer gifs" which are completely blank and therefore clearly provide no additional content.
Purely decorative images, such as work colleagues standing outside your business, serve as a visual break, dividing content and enhancing readability. An imaginative alternative text could be supplied, such as "image of employees posing dramatically against a blue sky" - but that's a description of the image rather than an alternative text, and it would not help someone who couldn't see the image to understand the page or use the site.
The Sitemorse Knowledge base is the repository of knowledge about the Sitemorse system.
Every time a new feature is added, a question asked or anything our technical team believe might be appropriate is recorded here.
- Understanding the tests conducted by Sitemorse
- Interpreting Sitemorse Reports
- Useful Technologies
- Sitemorse Surveys
- Function Diagnostics
- Accessibility Diagnostics
- Code quality
- Code quality Diagnostics
- Email Diagnostics
- Metadata Diagnostics
- Customer Service and Billing Questions
- Updates and development within Sitemorse