MySASSA

Accessibility

Last updated: 24 March 2026

SASSA grant information should be available to every South African who needs it, regardless of their device, connection speed, or ability. We have built MySASSA with this principle at its core.

Why This Matters for Our Users

We know who uses this site. Most of our visitors are accessing MySASSA from entry-level smartphones on mobile data, often with limited connectivity. Many are in rural areas where network coverage is inconsistent. Some may have limited literacy or be reading in a second or third language.

This is not an afterthought for us - it shapes every decision we make about how the site is built and how content is written.

Mobile-First Design

Built for phones first

Every page is designed to work perfectly on a small screen. Desktop is an enhancement, not the starting point.

Large touch targets

Buttons and links are sized at 44px minimum so they are easy to tap, even on small screens with imprecise touch input.

Readable text sizes

Body text is set at a comfortable reading size. We never use tiny text for important information.

Lightweight Pages

Data costs money, and slow connections are the norm for many of our users. We keep pages as lightweight as possible:

  • Minimal page weight - we avoid large images, unnecessary scripts, and heavy frameworks where possible
  • No auto-playing videos or audio that would consume your data without your consent
  • Content loads quickly even on 2G and 3G connections
  • Pages are designed to be functional even if some resources fail to load

Clear, Simple Language

Government processes and legal language can be confusing. We write our content with these principles:

  • Short sentences and paragraphs that are easy to follow
  • Plain English - we avoid jargon and explain technical terms when they cannot be avoided
  • Step-by-step instructions for processes like applying, appealing, or updating your details
  • Clear headings that tell you what each section covers, so you can find what you need quickly
  • Important information (like phone numbers and deadlines) is highlighted, not buried in long paragraphs

Technical Accessibility

We aim to follow web accessibility best practices, including:

  • Semantic HTML structure with proper headings, lists, and landmarks for screen reader users
  • Sufficient colour contrast between text and backgrounds
  • All interactive elements are accessible via keyboard navigation
  • Descriptive link text that makes sense out of context
  • ARIA labels on navigation elements and interactive components
  • No content that flashes rapidly or could trigger seizures

What We Intentionally Avoid

No auto-playing videos or audio
No pop-ups that block content
No required account creation or login
No unnecessary animations that could be distracting or cause motion sickness
No CAPTCHAs or complex verification steps

Report an Accessibility Issue

If you experience any difficulty using our site, whether it is a technical barrier, a confusing page layout, or content that is hard to understand, please let us know through our contact page. We take every report seriously and will work to fix issues as quickly as we can.