Mike Barram
BlogTagsProjectsAbout
Blog
Tags
Projects
About
Published on
Monday, 9 February 2015

Catching up on accessibility techniques

Authors
  • avatar
    Name
    Mike Barram
    Twitter

Concern over whether my modal dialogs are accessible led on this series of articles:

A great starting point if you don’t know why your sites should be accessible:
http://alistapart.com/article/reframing-accessibility-for-the-web

  • https://www.marcozehe.de/2015/02/05/advanced-aria-tip-2-accessible-modal-dialogs/
  • http://accessibility.oit.ncsu.edu/training/aria/modal-window/version-2/
  • http://www.paciellogroup.com/blog/2014/09/web-components-punch-list/

The very dry formal stuff
http://www.w3.org/TR/wai-aria/

Some examples
http://www.w3.org/WAI/PF/aria-practices/#aria_ex

These link to real examples e.g. http://www.oaa-accessibility.org/examplep/grid1/

http://www.paciellogroup.com/resources/

http://www.paciellogroup.com/blog/2015/01/the-browser-accessibility-tree/

http://www.paciellogroup.com/blog/2014/12/using-aria-describedby-to-provide-helpful-form-hints/

http://www.paciellogroup.com/blog/2014/08/using-the-tabindex-attribute/

 Screen readers

http://webaim.org/projects/screenreadersurvey5/

Free screen reader http://www.nvaccess.org/ (donate if you can) You can change the voice from the notifications area and Preferences > Synthesizer

Discuss on Twitter • View on GitHub

Tags

uomuom-a11y

Previous Article

Getting a WebApi2 controller to return HttpStatusCode.Forbidden

Next Article

Updated error handling
← Back to the blog
githublinkedin
Mike Barram
•
© 2022
•
Mike Barram
Tailwind Nextjs Theme