Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Accessibility
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
====Web accessibility features==== Examples of accessibility features include: * [[Web Accessibility Initiative|WAI]]-AA compliance with the [[Web Content Accessibility Guidelines|WAI's WCAG]] * [[Semantic HTML|Semantic]] Web markup * (X)HTML Validation from the W3C for the page's content * CSS Validation from the W3C for the page's layout * Compliance with all guidelines from Section 508 of the US Rehabilitation Act * A high contrast version of the site for individuals with low vision, and a low contrast (yellow or blue) version of the site for individuals with dyslexia * Alternative media for any multimedia used on the site (video, flash, audio, etc.) * Simple and consistent navigation * Device independent * Reducing Cognitive load for decision making While WCAG provides much technical information for use by web designers, coders and editors, ''BS 8878:2010 Web accessibility β Code of Practice''<ref>[http://www.hassellinclusion.com/bs8878/ BS 8878:2010 Web accessibility β Code of Practice].</ref> has been introduced, initially in the UK, to help site owners and product managers to understand the importance of accessibility. It includes advice on the business case behind accessibility, and how organisations might usefully update their policies and production processes to embed accessibility in their business-as-usual. On 28 May 2019, BS 8878 was superseded by ''ISO 30071-1'',<ref>[https://www.hassellinclusion.com/iso-30071-1/ ISO 30071-1].</ref> the international Standard that built on BS 8878 and expanded it for international use. Another useful idea is for websites to include a web accessibility statement on the site. Initially introduced in PAS 78,<ref>[http://www.equalityhumanrights.com/footer/accessibility-statement/general-web-accessibility-guidance/ PAS 78] {{Webarchive|url=https://web.archive.org/web/20150703160227/http://www.equalityhumanrights.com/footer/accessibility-statement/general-web-accessibility-guidance/ |date=2015-07-03 }}.</ref> the best practice for web accessibility statements has been updated in BS 8878<ref>[http://www.hassellinclusion.com/bs8878/ BS 8878].</ref> to emphasise the inclusion of: information on how disabled and elderly people could get a better experience of using the website by using assistive technologies or accessibility settings of browsers and operating systems (linking to "BBC My Web My Way"<ref>[https://www.bbc.co.uk/accessibility/ BBC My Web My Way], [[BBC]], UK.</ref> can be useful here); information on what accessibility features the site's creators have included, and if there are any user needs which the site does not currently support (for example, descriptive video to allow blind people to access the information in videos more easily); and contact details for disabled people to be able to use to let the site creators know if they have any problems in using the site. While validations against WCAG, and other accessibility badges can also be included, they should be put lower down the statement, as most disabled people still do not understand these technical terms.<ref>[http://www.hassellinclusion.com/accessibility/ Example of an accessibility statement written by the lead-author of BS 8878].</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)