Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Accessibility - Tips, Tricks & Best Practices for Plugin Developers

1 084 vues

Publié le

OKC WordCamp 2016

Publié dans : Internet
  • Soyez le premier à commenter

Accessibility - Tips, Tricks & Best Practices for Plugin Developers

  1. 1. Accessibility Tips, Tricks & Best Practices for Plugin Developers
  2. 2. Hi, I’m Trisha Salas @trishacodes
  3. 3. “Accessibility is not a dark art” -@GarethFW, Head of Accessibility @BBC
  4. 4. Accessibility is… a moving target.
  5. 5. Accessibility is… good design.
  6. 6. Accessibility is… good, standards compliant website design.
  7. 7. Accessibility is… about giving equal access to everyone.
  8. 8. Accessibility is… easy to appreciate or understand.
  9. 9. YOU HAVE THE POWER TO AFFECT CHANGE! Why should I care?
  10. 10. Where do I Start? Good HTML is the foundation of accessibility.
  11. 11. Learn HTML Deeply
  12. 12. •Choose the tag that best describes the content •Avoid tricky hacks, and workarounds •Use HTML, CSS and javascript appropriately •Don’t skip alt attributes on images. Best Practices
  13. 13. What about testing? Check Keyboard Accessibility WAVE Chrome extension Access Monitor WordPress Plugin
  14. 14. Are Plugins Different?
  15. 15. Some Examples
  16. 16. Nav Focus: tabindex tabindex=“1" defines an explicit tab order. This is almost always a bad idea. tabindex="0" allows elements besides links and form elements to receive keyboard focus. It does not change the tab order. tabindex="-1" allows things besides links and form elements to receive "programmatic" focus.
  17. 17. ARIA Labels We needed to give screen readers a little more context for our footer navigation
  18. 18. Focus Styles The addition of focus styles to search fields adds a visual cue that removes ambiguity and allows the user to follow along with the keyboard focus.
  19. 19. (maybe)_Let WordPress Speak or how an inaccessible datepicker led to a neat idea.
  20. 20. Don’t be afraid to be wrong.

×