Decision Tree Examples
Parent document: https://www.w3.org/WAI/EO/wiki/Role-Based_Decision_Tree
Context
This page provides examples of checkpoints being processed through the decision tree, to determine which role should get their primary ownership in the project lifecycle.
Development (Front-End Developer)
Example 1
Checkpoint
- I want adjacent linked images and text links pointing the same URL to be merged into single links.
A Business Analyst are not concerned with such issues.
Q2: Is this visual design? No
A Visual Designer designed the images and layout but has little interest beyond confirming the final deliverable matches the intended presentation.
Q3: Is this content authoring? No
A Content Author wrote the text for the links but, like the Visual Designer, is unlikely to do more than proofread the final deliverable and confirm there are no typos or other content errors.
Q4: Is this UX Design? No
The UX Designer is likely to come up with the need for linked images and links. The UX Designer likely have worked with a Visual Designer to define what it should look like and create the images to use. Another task would be to ask the Content Author to create the text to go with the images. Since having a single link would be easier for all users it is likely a design principle a UX Designer would define as a standard.
Those steps are all design tasks. If this checkpoint was applied to a design document (such as a style guide) the UX Designer would be the Primary owner. But in this example the assumption is we are testing a completed page. So, in this context, the UX Design might be a Contributor or not involved.
Q5: Is this development? Yes
This checkpoint is highly dependent on the implementation to avoid creating two consecutive links. Since this guideline would likely be part of a common style guide it's unlikely that to be specified in the wireframes, comps or requirements. As a result it be up to the Developer to choose an implementation so the image and text are a single link.
Example 2
Checkpoints
- I want no important images needing text equivalents to be placed as CSS background images.
- I want the full description of complex images to be provided through the longdesc attribute.
Business Analysts are not concerned with such issues.
Q2: Is this visual design? No
The Visual Designer likely chose or designed the images but will have little input on how it is done.
Q3: Is this content authoring? No
The Content Author certainly would provide the full description of the image. Depending on the context the role may have also influenced the image and its purpose.
In that case the author may have identified the images as "important" along with the text description when providing them to the developer. By definition that is a design deliverable. If that situation they may be a Contributor. But this checkpoint is for testing the final deliverable so the Content Author has little input beyond that.
Q4: Is this UX Design? No
The UX Designer likely has significant influence on the situation described here. The role almost certainly to have specified the use of second location for the description and the where the destination content is located.
These decisions should have been clearly documented as a general site-wide approach in a style guide or for the specific case. If the question was asked for a design deliverable the UX Designer would be the primary owner.
In the scenario here (testing a final website), the UX Designer should have already provided this information. If so, the role might be a Contributor.
Q5: Is this development? Yes
These checkpoints clearly focus on implementation (CSS, longdesc). Since developers choose the CSS implementation it's their responsibility to use approaches that satisfy the needs or standards for the site. When provided content (text alternatives or long descriptions) it's up to them to use the appropriate techniques.
Example 3
Checkpoint
- I want "null" alt attributes (using alt="") to be used for images that are already described in text in adjacent page content.
- I want decorative images to be ignored by assistive technology
Business Analysts are not concerned with such issues.
Q2: Is this visual design? No
Images are created or chosen by Visual Designers. This includes whether they are truly decorative or have some meaning (and how that's communicated) is not part of their role.
Q3: Is this content authoring? No
The Content Author wrote the adjacent page content describing the image. As in Example 2, where the author may identify images as "important" the role should identify them in this instance as decorative. In both examples, the Content Author is unlikely to be anything other than a Contributor.
Q4: Is this UX design? No
The UX Designer, working with the Visual Designer, may define elements with images that are decorative. A simple example might be icon controls with text labels under or beside them as part of the site navigation or features.
In these cases the UX Designer should indicate the images are decorative. As with the previous examples, these might be defined in a style guide. And (again) if this checkpoint was applied to the design document the UX Designer might be the Primary owner.
But, as with the other examples, for a completed site this checkpoint already identified the image as being decorative. The designer is unlikely to be more than a Contributor.
Q5: Is this development? Yes
The first case for this checkpoint is very specific about the use of alt="". This almost always applies to images implemented using the <img> tag. If told that an image is decorative and uses <img> the developer should know that that alt is a required attribute and decorative images should be set it to a null string.
The second case is similar but more general. The Developer may choose to use another approach (such as CSS background images) which has the same effect as alt="" in <img>s. Whichever case or implementations are used the Developer role is still the primary owner since failure to meet this checkpoint has identified the image as decorative.
Design (Content Author)
Example 4
Checkpoints
- I want informative alternate text to be provided for images (i.e. not "spacer" or image file name).
- I want informative images to be described with a text equivalent (alt attribute or other equivalent means).
- I want alternate text for informative images to be both clear and informative.
- I want the alt text used for images with text in them and/or representing text to include all relevant text found in the image.
- I want the alt text value of images and linked images not to replicate any information that is already being conveyed by screen reader technology.
Business Analysts are not concerned with such issues.
Q2: Is this visual design? No
Though these checkpoints are about images presented it is clearly about the text describing them. It's not the Visual Designer's role to author any text.
Q3: Is this content? Yes
These checkpoints evaluate the quality of the content. Since the content author role owns all content this is who should create it and provide it to the developer.
There may be some discussion with the UX Designers as to whether that content should be part of the (visible) body copy. Regardless of implementation, it's still up to the content author to provide the text to the developer (or indicate it is decorative and should be ignored).
Example 5
Checkpoints
- I want images primarily conveying function to use the alt text value to describe their purpose, rather than what they look like.
- I want the alt text value of images and linked images not to replicate any information that is already being conveyed by screen reader technology.
Business Analysts are not concerned with such issues.
Q2: Is this visual design? No
As described in Example 3, the Visual Designer may have created or chosen the images but has little influence over text describing them.
Q3: Is this content? Yes
These checkpoints are about text for functional elements (buttons, links, controls) so they belong to the Content Author. Even though they are likely short phrases or individual words they are subject to the writing standards for the site.
It will be important for the Content Author to understand how the Developer will implement the components or links to provide the best experience. This should be defined in style guides and design patterns for common elements.
Those are design documents created by the design roles. If these checkpoints were applied to them then the UX Designer would be the Primary owner since they are not specific to any content the author prepares.
If new, page-specific components are created the roles should discuss the implementation so the content author can adjust the text to avoid unwanted duplication or confusion.
Design (UX Designer)
Example 6
Checkpoints
- I want different ways to navigate the site such as site search, consistent menus, breadcrumb links and possibly a site map.
- I want instructions to on how to correctly enter information.
- I want error messages presented by each field with incorrect values.
- I want a confirmation screen to review before any final form submission.
- I want a warning message before time limits are about expire and the ability to continue.
- I want the ability to stop any automatically updating content like carousels.
Business Analysts may be concerned about forms or other features but rarely at this level.
Q2: Is this visual design? No
These checkpoints have presentation aspects but they are centered around core functions or feature definition that come before defining their presentation .
Q3: Is this content authoring? No
Text content is definitely involved with all of these checkpoints but, as with visual design, authoring would come after deciding how they will be implemented.
Q4: Is this UX Design? Yes
These checkpoints define primary features and operation that are the responsibility of the UX Designer. Decisions on features typically come early in product definition in functional specifications, requirements or user stories before any final presentation, content or implementation begin.
The UX Designer will almost certainly work with the Visual Designer to work out the presentation of these features and have the Content Author provide the text used. Depending on the technical requirements Front-End Developers may be consulted to confirm the feasibility which may influence the UX Designers options.
Example 7
Checkpoints
- I want the keyboard focus to advance across the page in a meaningful way.
- I want links to allow skipping past repetitive sections of page elements (like header navigation) when using the keyboard.
- I want logical, predictable keyboard operation when interacting with any user interface component, especially any that are not standard HTML.
Business Analysts are not concerned with such issues.
Q2: Is this visual design? No
These examples mainly center on keyboard operation, not presentation, which is not the Visual Designer's primary concern.
Q3: Is this content authoring? No
Similarly to the Visual Designer, these checkpoints are about keyboard operation, not content. The Content Author would only be asked to provide text after the decision has been made and only if any is needed at all.
Q4: Is this UX Design? Yes
Checkpoints about keyboard operation and user interaction are the domain of the UX Designer. They rely on understanding the needs of the users which a key responsibility of that role to interpret and define.
To the extent there is a visual aspect to operational checkpoints, the UX Designer may consult with the Visual Designer. The same is true when considering any text presented to users and the need to consult the Content Author. The UX Designer should provide Front-End Developers with specifications about keystrokes and operation but may not need to consult with them to make these decisions.
Design (Visual Design)
Example 8
Checkpoints
- I want contrast to be high enough that I can easily read all the text on the page.
- I want to easily see and identify which elements on the page I can interact with, especially keyboard focus.
Business Analysts are not concerned with such issues.
Q2: Is this visual design? Yes
These checkpoints are about selection of color and presentation. The Visual Designer provides the final choices in nearly all such situations.
The UX Designer might be consulted about requirements or options, but normally defers the ultimate decisions to the Visual Designer. Since there is no specific text in these checkpoint the Content Author is unlikely to be involved at all. Unless the Visual Designer is familiar with the limits of CSS and web presentation the Front-End Developers is probably will not be involved either.
Example 9
Checkpoints
- I want page content to still be readable and complete if the screen is magnified or the text size and spacing is changed.
- I never want to scroll page content horizontally on narrow screen widths or after magnifying text size and spacing.
Business Analysts are not concerned with such issues.
Q2: Is this visual design? Yes
Any issues about font presentation are almost always the sole responsibility of the Visual Designer. This includes deciding how to manage any overriding of the original, intended design. Other than providing the details to the Front-Designer, there is rarely any consultation with other roles on such presentation-centered topics.
In cases of responsive design (including preventing horizontal scrolling) the Visual Designer likely still makes the final presentation decisions. Unlike font-specific issues, there's an almost certain need to consult with the UX Designer on how to adapt to the constraints, especially on how and what to present interactive elements like navigation, links and controls. These complexities also likely require input from the Front-End Developer but only to help the Visual Designer define the final presentation. Content Authors, unless there are specific needs to define final text, are not likely to be actively involved.