-
Notifications
You must be signed in to change notification settings - Fork 7
Redesign
Feature-centric, in the style of "caniuse.com"
#Terms
- Feature: a rather fine-grained concept which contains one or more tests
- Top-level category: Contains many features. There aren't too many top-level categories.
- Test: An action for a reading system user to perform that tests one thing and can be answered yes or no.
- Content Documents
- Styling
- Scripting
- Font Embedding and Obfuscation
- Document Flow
- Media Overlays
- Global Language Support
- Content Fragment Identifiers
- Navigation
- Fixed Layout
List of features, organized by top-level category.
Notably absent: scoring
List of reading systems
Scores per-category
Notably absent: total score
Results for a single reading system
Organized by category, feature, test
Scoring at each level:
- Total score for all tests
- Category score for tests in that category
- Feature score given for all tests in that feature
- Test score itself given as pass/fail
Built into the URL - something like epubtest.org/feature/fxl/orientation
Show all reading systems' scores for this feature. The score will be given as none, partial, full, and expressed as passed/total (e.g. 5/7)
- Use external file to group tests into features. Not putting this info in the EPUBs themselves because it is only of concern to the website.
- Don't worry about database migration because we can just export and import the data instead of painstakingly dragging the database along.
How to make a testsuite more generic so that we can use the same mechanism for the accessibility testsuite as for the mainstream BISG one?
Right now, the scoring is very different for accessibility. Maybe represent the objects the same way but use a different scoring strategy.