Accessibility While You Edit
The accessibility tooling built into the editors, and which guide applies to you.
Both of Gallaudet's editing surfaces run an automated WCAG 2.2 AA check, but they behave differently — one blocks, one advises. Which guide you need depends on where you actually work.
Which editor do you use?
| If you edit at… | You are using | Your guide |
|---|---|---|
/guce_dash/ |
The Gallaudet Content Editing System (GUCE) | In the GUCE editor |
/wp-admin/ — Block Editor or Elementor |
The WordPress admin | In the WordPress admin |
Most department web editors use GUCE. If you are not sure, the editor at
/guce_dash/ is the one you reach from the Gallaudet Google sign-in.
The difference that matters
That asymmetry is intentional, but it means a page published from wp-admin can go live with issues nobody has seen. If you work there, running the audit before you publish is the only thing standing between a barrier and a real user.
What automation cannot do
Both audits use axe-core, which checks what is machine-checkable: missing alt text, contrast, form labels, heading order, empty links. It cannot tell you whether your alt text is meaningful, whether your reading order makes sense, or whether a table still conveys its meaning read linearly.
The person publishing the page is the accessibility checkpoint. The automation only catches the obvious part.
In this section
-
Accessibility in the GUCE Editor (sign in required)
The accessibility audit built into GUCE: when it runs, what it checks, and what to do when it finds something.
-
Accessibility in the WordPress Admin (sign in required)
The ADA Audit button, the Media Library PDF badge, and the PDF to HTML converter in wp-admin.
