In most traditional web apps you can achieve a reasonable level of accessibility with semantic HTML and a good page structure. Rails apps are no different. The framework provides lots of handy Action View Helpers and they come with everything you need to make your app accessible. However, just like when writing plain HTML, it's easy enough to forget about crucial attributes and end up with a page that is not accessible.
This website aims to tackle some of the most important accessibility concerns that you'll need to address in a Rails apps. You can read more about the project here.
All images must have an
alt attribute. This allows screen readers to either describe relevant images to users or hide them if they're not relevant. Learn how to make images accessible in Rails apps.
Read more about accessible Images in Rails
The purpose of each form field should be clear. Missing labels are one of the most common accessibility issues in web forms. Learn how to use form helpers the right way.
Read more about accessible Forms in Rails
Dynamic page updates, including flash messages, need a bit more work to be accessible to assistive tech users. Learn how to use ARIA live regions to make flash messages accessible.
Read more about accessible Flash messages in Rails
Just like flash messages, custom validation errors are usually skipped by screen readers. Learn how ARIA live regions and ARIA roles can make your forms accessible to assistive tech users.
Read more about accessible Form validation in Rails
lang attribute to your HTML is an easy win. It helps render the text more accurately, load the correct pronunciation rules, and display video captions correctly.
Read more about accessible Document language in Rails