This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Double redirects

Jump to: navigation, search

This page lists pages that redirect to other redirect pages. Each row contains links to the first and second redirect, as well as the target of the second redirect, which is usually the "real" target page to which the first redirect should point. Crossed out entries have been solved.

Showing below up to 26 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

  1. Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text equivalents for img elements, area elements, and input elements of type image (edit) →‎ Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text alternatives for img elements, area elements, and input elements of type image →‎ Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type image
  2. Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type image (edit) →‎ Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text equivalents for img elements, area elements, and input elements of type image →‎ Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text alternatives for img elements, area elements, and input elements of type image
  3. Using a script load toggle for feature detection libraries to provide a conforming alternate version (edit) →‎ Creating a conforming alternate version for web pages which are designed to be responsive / progressively enhanced →‎ Creating a conforming alternate version for a web page designed with progressive enhancement
  4. F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows assitive technology to ignore them (edit) →‎ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows Assistive technology to ignore them →‎ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows Assistive technology to ignore them
  5. F38: Failure of Success Criterion 1.1.1 to markup decorative images and applets to be ignored by assistive technology (edit) →‎ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows assitive technology to ignore them →‎ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows Assistive technology to ignore them
  6. F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-text content used for decorative purposes only in HTML (edit) →‎ F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-presentation images and applets used only for decorative purposes in HTML →‎ F38: Failure of Success Criterion 1.1.1 to markup decorative images and applets to be ignored by assistive technology
  7. F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-presentation images and applets used only for decorative purposes in HTML (edit) →‎ F38: Failure of Success Criterion 1.1.1 to markup decorative images and applets to be ignored by assistive technology →‎ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows assitive technology to ignore them
  8. AccessiblePrices (edit) →‎ Failure of Success Criterion 1.3.1 due to marking up prices in a way which results in incorrect information →‎ Failure of Success Criterion 1.3.1 due to marking up prices a where the decimal is not shown but the visual presentation indicates the need for a decimal
  9. Making actions keyboard accessible by using the onclick event on WAI-ARIA controls (edit) →‎ Making actions keyboard accessible by using the keyboard event handlers with WAI-ARIA controls →‎ Making actions keyboard accessible by using keyboard event handlers with WAI-ARIA controls
  10. CSS providing sufficient contrast for placeholder text (edit) →‎ Providing sufficient contrast for forms →‎ Using CSS to provide sufficient contrast for forms
  11. Using ARIA Live Regions (edit) →‎ Using ARIA Live Regions or role=alert to Identify Errors →‎ Using ARIA role=alert or Live Regions to Identify Errors
  12. Using Aria role=dialog to expose a custom dialog (pop-up div box) (edit) →‎ Using Aria role=dialog to implement a modal dialog box →‎ Using ARIA role=dialog to implement a modal dialog box
  13. Using WAI-ARIA states and properties for range widgets (progressbar, scrollbar, slider, spinbutton) (edit) →‎ Using WAI-ARIA range properties for range widgets such as progressbar, scrollbar, slider, and spinbutton →‎ Using WAI-ARIA range attributes for range widgets such as progressbar, scrollbar, slider, and spinbutton
  14. Using aria-describedby (edit) →‎ Using aria-describedby to provide descriptions of objects →‎ Using aria-describedby to provide descriptions of images
  15. Using aria-labeledby (edit) →‎ Using aria-labelledby →‎ Using aria-labelledby to name controls
  16. Using aria-labeledby for 1.1.1 (edit) →‎ Using aria-labelledby for 1.1.1 →‎ Using aria-labelledby to provide a text alternative the serves the equivalent purpose
  17. Using aria-labelledby (edit) →‎ Using aria-labelledby to name controls →‎ Using aria-labelledby to name user interface controls
  18. Using aria-labelledby to name controls (edit) →‎ Using aria-labelledby to name user interface controls →‎ Using aria-labelledby to povide a name for user interface controls
  19. Using aria-labelledby to name user interface controls (edit) →‎ Using aria-labelledby to povide a name for user interface controls →‎ Using aria-labelledby to provide a name for user interface controls
  20. Using aria-labelledby to provide a text alternative the serves the equivalent purpose (edit) →‎ Using aria-labelledby to provide a text alternative that serves the equivalent purpose →‎ Using aria-labelledby to provide a text alternative for non-text content
  21. Using aria-labelledby for 1.1.1 (edit) →‎ Using aria-labelledby to provide a text alternative the serves the equivalent purpose →‎ Using aria-labelledby to provide a text alternative that serves the equivalent purpose
  22. Sing grouping roles to identify related form controls when using fieldset-legend is not practical (edit) →‎ Using grouping roles to identify related form controls when using fieldset-legend is not practical →‎ Using grouping roles to identify related form controls
  23. Headings using role=heading (edit) →‎ Using role=heading →‎ Using role="heading" to identify headings
  24. Using WAI-ARIA states and properties in a tree widget (edit) →‎ Using the WAI-ARIA aria-expanded state in a tree widget →‎ Using the WAI-ARIA aria-expanded state to mark expandable and collapsible regions
  25. Talk:Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text equivalents for img elements, area elements, and input elements of type image (edit) →‎ Talk:Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text alternatives for img elements, area elements, and input elements of type image →‎ Talk:Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type image
  26. Talk:Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type image (edit) →‎ Talk:Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text equivalents for img elements, area elements, and input elements of type image →‎ Talk:Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting text alternatives for img elements, area elements, and input elements of type image

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)