It is easy to not care about accessibility, mainly because we generally don’t see or understand how people with disabilities use our applications. Frankly, even usability testing can become an afterthought when it comes to building websites. There are lots of move parts to a website or an application, and it is hard to pause and ask can someone access this information using just their keyboard and/or a screen reader. The more accessible your website is, the more users you can reach and engage with your website’s mission or purpose.At Design4Drupal maintenance support plans in Boston, caring about accessibility became the central theme for my presentation, titled ’Webform Accessibility’. After I gave my presentation, I created Drupal Update #2979628: [meta] Improve Webform Accessibility and started fixing some obvious and not-so-obvious issues with the Webform module for Drupal maintenance support plans 8. Andrew Macpherson, one of the Drupal maintenance support plans Accessibility Topic maintainers, was kind enough to spend an entire train ride from NYC to Boston discussing (via Drupal maintenance support plans Slack) form related accessibility issues and how to resolve them.There are tools that can show you obvious problemsThe most common form accessibility issue I see across the web is a failure to provide descriptive labels for form inputs. Labeling form inputs makes it possible for a screen reader to describe what input value is expected, as well as determine how it’s going to be used. For example, a screen reader needs to be able to identify a website’s search box so that users can find content quickly. The solution is to provide a hidden label or title attribute to a site’s search…Read More
Source: New feed