Don’t skip heading levels (e.g., H2 to H4) to get a certain size<\/div>\n
If a heading style looks wrong, contact the web team \u2014 don’t work around it by choosing a different level.<\/div>\n <\/div>\n <\/div>\n <\/div>\n\n \n
\n
Text formatting<\/div>\n\n
\n
avoid<\/span>\n \n
Don’t use ALL CAPS for emphasis<\/div>\n
Screen readers may spell out all-caps text letter by letter. Use bold or a heading instead.<\/div>\n <\/div>\n <\/div>\n
<\/div>\n\n
\n
avoid<\/span>\n \n
Don’t use color alone to convey meaning<\/div>\n
Example: “required fields are in red.” A colorblind user can’t see the distinction. Add a label, asterisk, or text indicator as well.<\/div>\n <\/div>\n <\/div>\n
<\/div>\n\n
\n
do this<\/span>\n \n
Write out acronyms on first use<\/div>\n
Example: “Full-Time MBA (FTMBA)” the first time, then “FTMBA” after. Helps screen readers and users unfamiliar with Ross terminology.<\/div>\n <\/div>\n <\/div>\n <\/div>\n\n \n
\n
PDFs & downloadable documents<\/div>\n\n
\n
ask web team<\/span>\n \n
All PDFs added to the site need to be accessibility-reviewed before publishing<\/div>\n
PDFs from external sources, older files, and scanned documents are rarely accessible. Don’t link a PDF until it has been reviewed.<\/div>\n <\/div>\n <\/div>\n
<\/div>\n\n
\n
do this<\/span>\n \n
Label PDF links so users know they’re downloading a file<\/div>\n
Example: “Download the BBA Student Handbook (PDF, 1.2 MB)” \u2014 not just “Student Handbook.”<\/div>\n <\/div>\n <\/div>\n
<\/div>\n\n
\n
do this<\/span>\n \n
Whenever possible, use a web page instead of a PDF<\/div>\n
Web pages are easier to keep updated, are searchable, and are far more accessible by default than PDFs.<\/div>\n <\/div>\n <\/div>\n <\/div>\n\n \n
\n
Tables, complex layouts, and embeds<\/div>\n\n
\n
ask web team<\/span>\n \n
Data tables<\/strong> (curriculum schedules, stats, comparison grids) require special markup to be screen-reader accessible \u2014 always request help<\/div>\n This includes any table with merged cells, spanning headers, or more than one header row.<\/div>\n <\/div>\n <\/div>\n
<\/div>\n\n
\n
avoid<\/span>\n \n
Don’t use tables for visual layout only (e.g., putting text side by side)<\/div>\n
Tables are for data relationships, not column layout. Ask the web team for layout help.<\/div>\n <\/div>\n <\/div>\n
<\/div>\n\n
\n
ask web team<\/span>\n \n
Video embeds<\/strong> must include captions and a transcript. Coordinate with the web team and video producer before publishing.<\/div>\n <\/div>\n <\/div>\n <\/div>\n\n
\n
ask web team<\/span>\n \n
Infographics, charts, or diagrams<\/strong> that contain meaningful text or data need an accessible text alternative<\/div>\n The web team can add a text summary or data table alongside the image.<\/div>\n <\/div>\n <\/div>\n <\/div>\n\n \n
\n
When to ask the web team<\/div>\n