Designing with accessibility in mind starts with selecting the most inclusive format for your content. In many cases, converting a document to a web page improves access, readability, and usability — especially for users with assistive technologies.
When to create a web page
If the content is intended for the general public — such as information about academic programs, student services, admissions, accessibility resources, or other university-wide initiatives — it is recommended that it be provided in an accessible HTML format. This approach ensures broad compatibility across devices and assistive technologies, enabling all users to access essential information when engaging with the university.
Web pages are easier to update than PDFs or Word documents and help ensure ongoing accessibility.
HTML content adjusts more effectively to screen size and zoom settings, making it easier to read on phones and tablets.
Web pages offer better accessibility for forms, buttons, and dynamic features when built using web technologies such as HTML.
Web pages are easier to find through search engines, improving discoverability.
Properly coded web pages work more reliably with screen readers, magnifiers, and keyboard navigation.
Web pages benefit from the existing accessibility features of the Brock website, so it is easier to comply with AODA and WCAG 2.0 AA requirements.
When to use a downloadable document
If the content is meant for download or printing, an accessible PDF or Word version may be appropriate — especially if a web version is also available.
When formatting must be preserved for legal or branding reasons, PDF is acceptable, provided the file meets accessibility standards.
If the content already exists on an accessible web page, a downloadable version can be offered as an optional format.
Some accessibility barriers often found in PDFs and Word documents include:
- Missing document titles
- Incorrect reading order
- Improper heading structure
- Missing alt text for images
- Poor form labeling
- Inflexible layouts that don’t zoom or reflow properly
Web page vs. document summary
| Consideration | Web Page | Accessible PDF/Word |
| Public access and visibility | Preferred | Use with caution |
| Ease of updates | Easy to update | Requires updating document, resaving and re-upload |
| Mobile accessibility | Responsive | Often limited |
| Interactive elements | Fully supported | Limited, often fails checks |
| Search engine optimization | Indexed by default | Less visible in search |
| Legal/policy compliance | Stronger conformance | Must be fully accessible |
| Print or archive format | Can supplement | Suitable if properly tagged |