Information should be available in forms users can perceive.
This includes attention to contrast, alternative text, captions, structure and presentation that does not depend unnecessarily on one sensory channel.
Morganable
Access · Clarity · Usability · Inclusion
Access is not an extra layer.
It is part of whether public-interest knowledge is truly public.
Morganable aims to make its journalism, research, data and public-knowledge services usable by as many people as reasonably possible, including people who use assistive technologies.
01 / Read Legible information
02 / Navigate Predictable structure
03 / Operate Keyboard interaction
04 / Perceive Accessible media
05 / Understand Clear communication
06 / Improve Report and remediate
01 / Commitment
Morganable Accessibility
Usability is part of public value.
Morganable publishes journalism, research, data, analysis and institutional knowledge for public use. Making that work available is not only a question of whether a page technically exists. People must also be able to perceive, navigate, understand and operate the experience through which the work is delivered.
Accessibility therefore belongs across design, engineering, editorial production, multimedia, forms, downloadable documents and the continuing maintenance of Morganable’s digital services.
Different users may interact with Morganable through keyboards, screen readers, magnification, captions, alternative input methods, smaller displays or other assistive technologies and settings. Our approach should increasingly account for that diversity.
The question is not simply whether information was published.
The question is whether people can meaningfully reach and use it.
Accessibility Principles
Design for access before remediation becomes necessary.
Accessibility is stronger when it influences the architecture of a page, product or publication from the beginning rather than being treated solely as a corrective exercise after launch.
Interaction should not depend exclusively on a mouse.
Navigation, links, forms and interactive controls should increasingly support keyboard and other appropriate input methods.
Structure and communication should reduce unnecessary friction.
Labels, headings, instructions and interactions should make their purpose reasonably clear.
Content should work across changing technologies.
Semantic structure and established web practices can improve compatibility with browsers, assistive technologies and future interfaces.
Accessibility Architecture
From publication to
usable experience.
Accessibility involves several layers working together. Strong typography alone cannot compensate for inaccessible controls, and semantic code alone cannot compensate for unreadable presentation.
01
Structure
Organise pages with meaningful hierarchy, headings and semantic relationships.
02
Present
Use legible typography, sufficient distinction and layouts that remain understandable.
03
Navigate
Make links, focus order and page movement reasonably predictable.
04
Operate
Support keyboard interaction and accessible controls where functionality permits.
05
Communicate
Provide accessible alternatives and instructions for media, forms and complex information.
06
Improve
Identify barriers, receive feedback and remediate accessibility problems over time.
Accessibility Domains
Accessibility reaches across the whole publishing system.
These areas describe the principal accessibility considerations Morganable should continue to strengthen as its digital and knowledge architecture develops.
01 / Visual
Typography & Contrast
Legible type, clear hierarchy and sufficient visual distinction between text and backgrounds.
02 / Navigation
Keyboard & Focus
Operable controls, logical interaction order and visible focus states for keyboard users.
03 / Structure
Semantic HTML
Meaningful headings, landmarks and content structure that assist interpretation by technology.
04 / Images
Alternative Text
Useful text alternatives for informative images where equivalent information is required.
05 / Audio-Visual
Captions & Transcripts
Textual access to important spoken or audio information where practicable and appropriate.
06 / Input
Accessible Forms
Labels, instructions, error identification and operable input controls.
07 / Motion
Motion Control
Avoiding unnecessary motion and respecting reduced-motion settings where implemented.
08 / Responsive
Device Adaptability
Layouts that restructure across large screens, laptops, tablets and mobile devices.
09 / Documents
Downloadable Content
Improving the usability and accessibility of important PDFs and other downloadable materials.
Reading & Visual Design
Information should not become harder to understand because of presentation.
Morganable’s visual identity can remain distinctive while prioritising legibility, hierarchy and usable contrast across editorial and institutional pages.
01 Readable typography
Type size, line height and spacing should support sustained reading across devices.
02 Clear hierarchy
Headings and sections should help readers understand the relationship between parts of a page.
03 Colour contrast
Important information should retain sufficient distinction from its background.
04 Meaning beyond colour
Colour should not be the only way important status or meaning is communicated.
05 Responsive reflow
Layouts should restructure rather than simply shrink desktop architecture onto smaller screens.
06 Zoom resilience
Content should remain usable as users enlarge text or browser presentation where reasonably possible.
Keyboard & Interaction
Interaction should remain visible and operable.
Links and controls should increasingly support users who navigate without a pointing device and should make keyboard focus sufficiently visible.
01 / Focus
Visible Focus States
Keyboard users should be able to identify which interactive element currently has focus.
02 / Order
Logical Navigation
Focus movement should broadly follow a meaningful reading and interaction sequence.
03 / Links
Understandable Destinations
Link language should provide reasonable context about its purpose or destination.
04 / Controls
Operable Components
Interactive components should provide appropriate keyboard operation where applicable.
05 / Behaviour
Predictability
Controls should avoid unexpected behaviour that makes navigation unnecessarily difficult.
06 / Recovery
Accessible Errors
Users should receive understandable information when an interaction or submission fails.
Images, Audio & Video
Multimedia should expand access, not create a new barrier.
Morganable’s growing audiovisual work creates additional accessibility responsibilities around images, speech, important audio information and visual-only meaning.
Alternative Text
Informative images should increasingly include text alternatives that communicate the relevant content or purpose without simply repeating nearby text.
Avoid Unnecessary Noise
Purely decorative content should not create needless verbosity for assistive technology users.
Captions
Important spoken content should increasingly be supported by accurate captions where practicable.
Transcripts
Important audio-only material should increasingly provide a meaningful textual alternative where appropriate.
Motion & Device Adaptability
Dynamic design should remain controlled.
Movement can strengthen hierarchy and interaction, but unnecessary motion should not become a prerequisite for understanding or operating a page.
01 Reduced motion
Where implemented, interfaces should respect user preferences requesting reduced animation.
02 No essential meaning in animation alone
Important information should remain available without requiring a user to perceive an animation.
03 Responsive architecture
Complex desktop structures should reflow into appropriate tablet and mobile layouts.
04 Touch targets
Interactive controls should provide usable target areas where layout permits.
Forms & Input
A form should explain what it needs from the user.
Careers, contact, registration and other interactive services should increasingly provide usable labels, instructions, validation and error handling.
01 Labels
Input fields should have meaningful labels rather than relying only on placeholder text.
02 Required information
Required fields and important conditions should be reasonably identifiable.
03 Instructions
File restrictions, formats and other input requirements should be communicated clearly.
04 Error identification
Submission problems should provide information useful for correcting the error.
05 Keyboard operation
Form controls should remain reasonably operable without exclusive dependence on a mouse.
06 Confirmation
Important submissions should provide understandable confirmation when successfully received.
Downloadable Documents
Accessibility should not end when a user leaves the webpage.
Reports, research papers, data documentation and other downloadable materials can create accessibility barriers even where the surrounding webpage is usable.
Document Hierarchy
Important documents should increasingly preserve meaningful headings and reading order.
Readable Presentation
Text size, contrast and document layout should support reasonable reading conditions.
Web Equivalents
Where feasible, essential information should not exist exclusively inside an inaccessible file format.
Language & Understanding
Complexity should come from the subject, not unnecessary obscurity.
Morganable covers complex subjects and should not remove necessary precision merely to simplify language. But complexity should be explained where explanation can improve understanding.
Accessibility does not require making serious work simplistic. It requires making complexity navigable.
Descriptive headings Navigation
Defined specialist terms Clarity
Useful summaries Orientation
Logical sequencing Structure
Context around data Understanding
Precision without unnecessary jargon Language
How We Think About Accessibility
Some accessibility questions require continuous rather than one-time answers.
These principles describe Morganable’s intended approach as its websites, products and knowledge services continue to develop.
01 Is accessibility complete once a page launches?
No. Websites change, browsers change, content changes and new components are added. Accessibility therefore requires maintenance, testing, feedback and remediation rather than a single design decision.
02 Does accessibility mean removing premium design?
No. Strong visual identity and accessible interaction can coexist. The design challenge is to preserve distinction without sacrificing legibility, usability or meaningful alternatives.
03 Are all historical Morganable materials guaranteed accessible?
No such blanket claim is made here. Older pages, third-party components, archived documents or legacy content may present accessibility limitations that require continuing remediation or alternative access.
04 What if I encounter an accessibility barrier?
Users can contact Morganable and identify the page, document, control or content that is difficult to access. Specific information about the barrier can help us investigate and prioritise an appropriate response.
Standards & Claim Discipline
Accessibility claims should be evidence-based too.
Morganable can use recognised accessibility standards as important design and engineering references without turning aspiration into an unsupported certification claim.
Morganable should not claim formal accessibility certification or a particular conformance level until appropriate testing supports that claim.
The accessibility practices described on this page represent Morganable’s intended institutional approach and continuing direction. They should not be interpreted as a claim that every page, document, third-party component or historical asset currently satisfies every criterion of a particular accessibility standard.
Report An Accessibility Issue
If something is difficult to access, tell us what happened.
Specific accessibility feedback can help Morganable identify barriers that automated checks or ordinary editorial review may not reveal.
Accessibility Feedback Please identify the page, document or feature and describe the barrier you encountered.
Where possible, include the URL, device or assistive technology involved and the task you were trying to complete. You do not need specialist accessibility terminology to report a problem.
Contact Morganable → Continuous Improvement
Accessibility is a continuing operational responsibility.
Morganable’s digital architecture will continue to evolve. Accessibility should therefore remain part of design review, production, engineering and remediation.
01 Design
Incorporate accessibility considerations before complex interfaces are finalised.
02 Build
Use semantic and interaction patterns that support accessible implementation.
03 Review
Examine new pages and features for accessibility risks before and after publication.
04 Test
Expand practical accessibility testing as institutional capability develops.
05 Listen
Use credible user feedback to identify barriers that internal review may miss.
06 Remediate
Prioritise meaningful barriers and document improvements where appropriate.
Morganable Accessibility Make the knowledge available.
Make the knowledge available.
Make the path understandable.
Make access part of the work.
Morganable’s accessibility approach is part of a wider commitment to public-interest journalism and knowledge: information should not only be published, but increasingly designed so that more people can perceive, navigate, understand and use it.
