You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{# Create a temporary ID and add it to the map: #}
@@ -304,11 +304,11 @@ Note that we’re creating a two-way binding between the `tab` and `tabpanel`:
304
304
305
305
## Testing and auditing
306
306
307
-
The best time to start auditing your front-end for accessibility is during development.
307
+
The best time to audit your front-end for accessibility is during the design phase. The next best time is during development.
308
308
309
-
As you build out your templates, tools like Deque’s [Axe DevTools for Web](https://www.deque.com/axe/devtools/web-accessibility) can flag concrete violations and help you prioritize remediation.
309
+
As you build your templates, tools like Deque’s [Axe DevTools for Web](https://www.deque.com/axe/devtools/web-accessibility) can flag violations and help you prioritize remediation.
310
310
311
-
To monitor the accessibility of content and quickly identify issues that crop up after launch, consider using a tool like [Accessible Web](https://accessibleweb.com/)’s [automated scanning tool](https://accessibleweb.com/ramp-web-accessibility-tools/accessibility-monitoring/).
311
+
To monitor content accessibility and quickly identify issues after launch, consider using a tool like [Accessible Web](https://accessibleweb.com/)’s [automated scanning tool](https://accessibleweb.com/ramp-web-accessibility-tools/accessibility-monitoring/). Keep in mind that automated scans catch only a fraction of accessibility issues, and manual testing should also be part of your process.
312
312
313
313
Set up a [custom source](../system/elements.md#sources) for your assets using the **Has alternative text** condition rule to give authors a central place to remedy missing image descriptions:
0 commit comments