Development of the AASPIRE Web Accessibility Guidelines for Autistic Web Users

Lay Summary: This guideline is a summary of the accessibility features we identified and implemented during the course of our study. None of these items were difficult or expensive for us to implement. They did not require special expertise beyond basic web programming and technical communications skills. We recommend that anyone seeking to create accessible websites for autistic users follow the Academic Autism Spectrum Partnership in Research and Education (AASPIRE) Web Accessibility Guideline in addition to broader web and communications standards and principles.Physical accessibility:Provide at least one low-contrast neutral color palette option to accommodate sensitive vision.Provide a selection of color palettes, including one with a dark background and one with a light background, again to accommodate color and contrast sensitivity.Provide a no-style option (i.e., no cascading style sheets (CSS) to accommodate browser customization and users who prefer no stylistic formatting.Provide simple consistent navigation and highly consistent site behavior for increased ease of operation.Avoid textured backgrounds, moving images, decorative elements that do not convey information, and other visual and/or sonic "clutter"; these types of elements may make the site difficult or impossible to comprehend.Provide smaller font sizes in addition to larger ones; large font sizes may make the page appear cluttered and difficult to read.Use a plain accessible sans-serif font (e.g., Arial) for ease of readability.Intellectual accessibility:Use the simplest interface possible for ease of understanding.Use simple concrete icons or images to communicate redundant information with text, and accommodate multiple ways of understanding information.Clearly label site elements with their purpose everywhere on the site, even if it seems redundant, to make navigation and site functionality easier to follow.Provide concrete examples where applicable to accommodate difficulties in understanding abstractions or generalizations.Minimize scrolling so the user does not need to rely on assumptions about content to guess what might be on the page.Show all important features and site navigation (as opposed to within combo box drop-down areas) so the user does not need to rely on assumptions to guess whether the item exists and how to access it. For example, completely visible list boxes or radio buttons can be used instead of combo boxes.Make content as short as possible without sacrificing precision and specificity, to reduce cognitive burden.Social accessibility:Be specific and precise in language use; avoid colloquialisms, idioms, and ambiguity to accommodate difficulties with language pragmatics.Explain the reason behind any nonstandard instructions or unusual information; provide additional pragmatic context to accommodate difficulties with language pragmatics.Provide alternatives to definitive response items on surveys and forms, for example, "do not know," "do not wish to say," or "not applicable," to reduce frustration for not being able to produce an exact answer.Use FAQ formats to organize complex information to enhance clarity as to why the information might be useful to the user and how it connects to their life.Define terms that might have different meanings depending on social context, or which might be jargon related to a specialized field (e.g., "drug interactions" and "health care providers"), to accommodate difficulties with language pragmatics.Be mindful of autistic culture and community preferences, including the language used to describe autism and how community-based symbols and history might influence content and perception of site credibility.