Using Gherkin To Write Accessibility Tests
By Gemma Pitman | 2nd November 2017
A practical guide on how to write accessibility acceptance tests using the gherkin syntax whilst using the BDD methodology
Further Navigation
Categories
Tags
- Accessibility
- ADD/ADHD
- Agile
- Agile development
- AI
- alzheimers disease
- Amazon Echo
- Aspergers
- Assistive technologies
- Autism
- Automation
- autonomous vehicles
- Autoplay
- AUX
- B2B inclusion
- Banking
- Barclays
- BDD
- boutique shopping
- Browser extensions
- BSL
- built environment accessibility
- Christmas
- Code
- Communication
- Community leads
- customer service
- Dave Padgen
- Deaf
- Deaf culture
- dementia
- Design tips
- Desktop
- Developer accessibility hacks
- Disability confidence
- disability statistics
- Dyslexia
- Dyslexia awareness week
- Dyspraxia
- Education
- Elderly
- emerging technology
- Financial services
- FinTech
- future of digital accessibility
- GAAD18
- Gherkin
- Headings
- immersive technology
- Inclusion
- inclusion speed dating
- Inclusion statistics
- inclusive design
- inclusive events
- inclusive research
- Independent living
- Individual adjustments
- innovation
- insight
- Julia Fernandez
- Kids
- Landmarks
- Links
- London a11y Meetup
- M&S
- market data
- Mike Adams
- Navigation
- Nelly McCabe
- Neuro-diversity
- Open banking
- Personal adaptation
- Plugins
- Podcast
- Pragmatic accessibility
- PSD2
- Purple
- purple pound
- Purple Tuesday
- QA
- retail
- retail inclusion
- ROI in inclusion
- Role attributes
- Scope campaign
- Shani Dhanda
- sign language
- Social interaction
- Special Assistance services
- staff training
- STTR
- supermarkets
- Testing
- Travel
- Universal design
- User research
- Vision impairment
- WALL18
- Wordcamp
- WordPress