Refer to the U.S. Web Design Standards on alerts for accessibility and usability guidelines. We have one addendum:

Usability

• The Standards state: "Allow a user to dismiss a notification wherever appropriate." We believe it is appropriate to globally state that all alerts below the level of error should be dismissible. Errors should not be dismissible because they should only be present when the user cannot continue and/or is required to take action.

Usability

When to use

• To draw attention to a particular piece of functionality.

When to consider something else

• A tip should not be used when one of the other contextual help elements is more approriate.
• A tip should not be used in place of an alert.

Guidelines

• Each tip is dismissible and include a primary CTA button.
• The counter (1 of 2 tips) and secondary CTA button (Skip) is only shown if a user has 2 or more tips.
• Clicking the Skip button will trigger the next tip (if applicable). Clicking the Back button will show the previous tip (if applicable).
• Tip lifespan: The dismiss and skip buttons do not remove the tip permanently. If a user dismisses or skips a tip, then the tip will be shown again the next time the user restarts their browser (and thus a new browser session is created) or 2 weeks, whichever comes first. The tip will no longer be shown once the suggested action has been taken. For example, the tip will continue to appear until the suggested document upload has been completed.

Examples

DD-214

This tip is shown if the user indicates in their profile that they are:

• A veteran AND claim veterans' preference.

Regardless of veteran status, this tip will not be shown if the user indicates in their profile that they do NOT claim veterans' preference (selects the "No, I do not claim Veterans' Preference" radio button option). The tip will continue to appear on the Documents page until the document is uploaded.

Tip Title

Do you want to claim veterans’ preference?

Body copy

If so, we recommend you upload your DD-214 – it’s required if you want to claim veterans’ preference.

SF-15

This tip is shown if the user indicates in their profile that they are:

• A veteran AND claim veterans' preference.

Regardless of veteran status, this tip will not be shown if the user indicates in their profile that they do NOT claim veterans' preference (selects the "No, I do not claim Veterans' Preference" radio button option). The tip will continue to appear on the Documents page until the document is uploaded.

Tip Title

Do you want to claim veterans’ preference?

Body copy

If so, we recommend you upload your SF-15 – agencies will often request this form to verify your veterans’ preference.

SF-50

This tip is shown if the user indicates in their profile that they are:

• Currently a federal civilian employee.
• A former federal civilian employee with reinstatement eligibility.

This tip will not be shown if the user indicates in their profile that they are:

• Not and have never been a federal civilian employee.
• A former federal civilian employee but DO NOT have reinstatement eligibility.

The tip will continue to appear on the Documents page until the document is uploaded.

Tip Title

Your profile says you are or were a federal employee.

Body copy

We recommend you upload your SF-50. Many jobs require the SF-50 to verify your federal service.

Profile Tips and Alerts

Success message - Contact information saved

This alert displays when a user has updated or completed their contact information, but has not completed their eligibility section.

Tip Title

Contact information saved.

Body copy

Your contact information has been saved to your profile. You have completed 1 of 2 required sections in your profile. You need to complete the Eligibility section, before you can apply for jobs.

Call to action

Next: Eligibility

Info message - No preferences in profile

This alert displays when a user has updated their profile but has not specified any preferences.

Body copy

We noticed you don't have any profile preferences. You can improve you search results if you update and use your preferences. Update your preferences.

Info message - User who have not updated their profile in over 6 months

This alert displays for signed in users when they have not updated their profile in over 6 months.

Body copy

It's been over six months since you've signed in. Is your profile up-to-date? Update your profile.

Usability

When to use

• Use at the bottom of forms to demarcate the end of the form and highlight the call to action (save, update, next, etc.).
• Use the default variation to associate two buttons together (previous/next, save/cancel, etc.).
• Use the slim variation when there is only one button.
• Use the slim, left-aligned variation in edge cases when there is only one button and content is weighted towards the left. The button bar doesn't always adhere to the input max-width and thus can float far to the right, potentially creating issues for users pointing to the right-aligned button (See Fitts's Law).

  Do not use this variation if using the other button-bar variations within a flow. Using this variation is allowed at the start or end of a flow, however don't switch variations mid-stream.

Requirements

When to use

When to consider something else

Requirements

• Spacing: A card always includes at least the default size (15px) of padding. Margin can be overrode as necessary to allow cards to fill the viewport on smaller hand-held devices.
• Title: The title of the card in a list is often a title of the object it describes. Titles and names can be long thus in a card they span the full width of the card.
• Shadow: Cards always have some box-shadow applied to give the appearance of depth excluding when they are presented in a list of 10 or more where the shadow creates a radiating pattern (see list variation below). The card above is at level 1. Levels can be increased up to level 5 to give greater depth and separation but should only be done so sparingly. Level 1 is the default.

When to use

• The uses of cards are too numerous to mention.

When to consider something else

• Avoid cards for long content. If the focus is reading the content then the card will likely just get in the way and be visual noise.

Requirements

• All of the aforementioned card requirements from the Card - Large variation excluding the box shadow. Box shadow on cards that are in a list of 10 or more creates a radiating visual pattern that is distracting and thus should be avoided. It also takes up space that isn't appropriate in a long list.

When to use

• In a list context where many cards will be right next to one another.

Guidance

• The first line of the document details is the user-provided title of the document.
• Title truncation: 8 characters at the start and end of the filename MUST be visible. For example, if the uploaded file name is "My-long-document-name-that-is-too-long-to-show.doc" then it woulbe abbreviated to "My-long-…show.doc". This keeps the title on one line. The desire is to handle document names that have a suffix that is important to the user (e.g. "-1") and to include the mime type of the file.
• The second line of a document, NOT a resume, is the document type which is one of:
  • Cover Letter
  • DD-214
  • ECQ
  • OF-306
  • Other
  • SF-15
  • SF-50
  • Transcript
  • Veteran Other
• Resumes either uploaded or created by the resume builder do not get a document type in Application Guide.
• The third line of a document is the date the document was uploaded. This line of text is in the format "Uploaded [date]". Resumes created by Resume Builder are in the format "Built [date]".
• The View link opens the full document in a modal.
• The Delete link will open a dialog in a modal asking the user to confirm removal of the document.
• For resume documents that are built with Resume Builder the View link is replaced by an Edit link. Clicking that link will open the Resume Builder in a new target (tab or window).

Usability

When to use

• Whenever a document has been uploaded to USAJOBS use this component to reflect the document back to the user.
• Use the single-select version, which contains a radio button input, when only a single document can be selected from a series of documents (i.e. resume).
• Use the multi-select version, which contains a checkbox input, when multiple documents can be selected from a series of documents.
• Use the loading animation when the document has been uploaded and the thumbnail is loading into this component.

Do not use when

• The document has not been provided by the user (i.e. the document is pubished by USAJOBS).

Guidelines

Usability

When to use

• Use this variation in cases where the document thumbnail does not exist or cannot be loaded.

Usability

• Affordance: The drawer trigger needs to have sufficient affordance. That is achieved by the combination of the drawer handle (plus/minus button) and the drawer title (primary blue to match links) in close proximity to one another (same line) in a list of similar items (other drawers). This combination of elements should be retained otherwise the drawer may lack the affordance for users to know that this component will reveal additional content.
• Title: The title of the drawer in a list is often a title of the object it describes. Titles and names can be long thus in a drawer, as in a card, they span the full width of the component. Titles should be truncated coming out of the database rather than inserted into the component and allowed to line wrap. Because titles can wrap due to their length they should not be underlined.
• Shadow: The drawer content has an inset shadow to strengthen the relationship between the drawer button plus face and the drawer contents.

When to use

• This variation of drawers can be used when you want to list content where more context may be needed to differentiate the items in a list. In other words, if the user may need to see some details about the object being described in order to discern one from the other in a list. Examples include job applications and elements of a user's profile (education, experience, languages, references, etc.)

When to consider something else

• Avoid drawers when the details are vast. For example, we specifically did not employ this pattern in search results where the details of a job are too numerous to include within a drawer. It's less about number of items revealed and more about the length of the content within the drawer. If the drawer contents could be in their own view/page then perhaps a list of links would be preferred.

When to use

• This variation of drawers can be used when you have clear actions supported by iconography.

Guidelines

Usability

When to use

• Used on the landing page within a container to highlight events.
• To be used within search results for queries that include a location and/or hiring path in order to highlight relevant events.

Our "fat footer" provides secondary navigation for the site. It reflects the new structure of the site and provides a quick and easy way for users to jump to a specific sub-section. It also sensitizes users to the new structure by exposing sub-sections that help explain what can be found in each area of the site.

Accessibility

Please refer to the U.S. Web Design Standards for accessibility and usability guidance.

Implementation

• The "Return to top" link should be an anchor link to the page title (h1) of the current page.
• The "Sign Out" link is dropped when the user is not authenticated.

Usability

When to use

• The footer should appear on all pages excluding the Application Guide.

Do not use when

• Do NOT add the footer to the Application Guide path. When users are focused on completing their job application we do not want to distract them nor take them off that path.

Version details

• Version 3 reverts the use of font awesome and utilizes SVGs with PNG fallbacks. In order to remove font awesome versions 1 and 2 of the footer are no longer supported.

Usability

When to use

• This variation of the footer is used on the job announcement page as it contains a different set of small links at the bottom of the page which are required to include.

Usability

When to use

• This variation of the footer is used in the Open Opportunities application.

Usability

When to use

• This variation of the footer is used on pages where navigation away from the page is not desired such as authentication pages.

Guidelines

Print

• Clicking "Print" opens the job announcement print-preview view in the same window.

Share

• Clicking "Share" toggles a popup menu of choices.
• Clicking any of the choices opens a new window that shares the URL of the job announcement via that service (email, Facebook, Google+, LinkedIn, Twitter, or TinyURL) and closes the share menu.

Save

• A job announcement that has not been saved starts out in the state shown above with the text "Save" and the unfilled star icon.
• Clicking "Save" or the star icon will update the text to "Saved" and fill the icon. The job should be saved at that time to the user's list of Saved Jobs.
• Clicking "Saved" or the star icon will update the text to "Save" and un-fill the icon. The jobs hould be removed at that time from the user's list of Saved Jobs.

Usability

When to use

• Use inside a job announcement to allow the user to apply to, print, save, or share the job.

Guidelines

• "Agency contact information" is a sub-section of the How to apply section.
• v1.6 adds a "When to contact the agency" section that details when and why to contact an agency about a job. This section is being revised.

Usability

When to use

• Use inside the "How to apply" section and the agency modal.

Accessibility

• The links in the "This job is open to" section MUST be bold in order to meet contrast requirements given that the link color is blue and the background is blue.

Guidelines

• Open & closing dates are now combined into one field. The clock icon should appear yellow when the closing date is within a week and red when it is within 48 hours.
• Salary values should not show cents when the rate is per year. For example, "$100,000" instead of "$100,000.00".
• Pay scale - There must be a space between pay scale and grade(s).
• Grade - multiple - When a position is open across more than one grade level a dash should be used to separate the lowest and highest grade. For example, "05 - 09".
• Grade - single - When a position is open in only one grade level only a single grade level should be shown. For example, "05".
• Series number is shown, with leading zero when appropriate, in front of the series name.

Hiring paths

• This job is open to is a new section that begins to replace the "Who May Apply" section. It is generated either by parsing the text of "Who May Apply" or through use of the Hiring Path Codes now available via the SIF.
• Clarification from the agency is a new section that appears when an agency supplied the Hiring Path Codes AND the Hiring Path Explanation text. It should only appear when both the Codes and Explanation have been provided.
• Who May Apply continues to appear on the page. It is now found at the bottom of the Duties section. There is a link inside of the section that anchors back to "This job is open to" in order to help users through this transitional period where both sections are present. Once agencies have had a chance to adjust to the SIF changes that require the new list of hiring paths and move other "pre-requisites" to their appropriate sections the Who May Apply section will be removed.
• The "Special authorities" hiring path will require text in this field to identify the appropriate authority.
• This job is open to and Hiring paths are explained in greater detail in the Job announcement playbook.

Locations

• 4 locations are displayed at all view points with any additional locations hidden behind a reveal show more/less toggle. Expanding the toggle reveals all additional locations. Collapsing the toggle hides those additional locations.
• The number of vacancies is required via section 1105 of Title 5, U.S.C. and thus must be specified and displayed next to each duty location.

Application closing types

There are four ways that an application can close. The following lists those types and provides the text that should be shown:

• Closing date: No additional text is shown.
• Closing time: You must complete this application process and submit any required documents by xx:xx pm. Eastern Time on the closing date of this announcement.
• Open continuous: This job is open continuously and will remain open for an extended period of time. We will fill jobs as they become available. Learn more.
• Applicant cut-off: This job will close when we have received [ApplicationCutOff #] applications which may be sooner then the closing date. Learn more. (This variation is shown above.)

Second announcement type

If a second announcement is also open to different set of hiring paths then that announcement is indicated below the "This job is open to" section.

• If the second announcement is open to multiple hiring paths then the top most in the list is selected. For example, if a job is open to only merit promotion eligible Federal Employees and is currently being displayed and that same job is open to the public and an addition hiring path the second announcement link would indicate the open to the public icon and text. The ordering for selection is as shown above.

Usability

When to use

• Use inside a job announcement to introduce the job to the user and to explain who is eligible to apply to this announcement.
• Not all hiring paths in the "This job is open to" section require meta text describing that eligibility. In testing we found that users were able to self-identify into one or more of these categories. The paths that do have meta text required either a bit of clarification for some sub-sets of job seekers or text to further clarify the label.

Accessibility

• The links in this section MUST be either bold or 19px in order to meet contrast requirements given that the link color is blue and the background is blue.

Guidelines

• This is a new section (as of release 6.6) and a revision to that section that adds mission critical occupations.

Job family (Series)

• Displays each series associated with the job.
• The series will have a blue dot prefix (triggered by the class .is-mco) when it is a series defined as mission critical. The list of mission critical series matches the series displayed on the landing page.

Related occupations

• Displays up to 6 SOC occupations that match the job and the count of total jobs, including this one, that search returns for that occupation.

Explore...

• Highlights mission critical occupations using either the Mission critical code or a fall-back URL as defined below.
• If there are 1 or more jobs tagged using the Mission critical code then the link points to search results with that filter applied. A pill is added to represent that tag using the value of the tag name.
• If there are 0 jobs tagged using the Mission critical code then each tag has a "fallback" URL as follows:
  1. Cybersecurity: https://www.cybercareers.gov/
  2. Data Science: https://www.usajobs.gov/careerfields/data-science/
  3. Economist: https://www.usajobs.gov/Search/ExploreOpportunities/?Series=0110
  4. Grants Management: https://www.usajobs.gov/Search?j=1109
  5. Privacy: https://www.fpc.gov/
  6. Program/Project Management: https://www.usajobs.gov/Search?j=0340
  7. STEM: No fallback - do not show the link

Job that are in high demand... (Key)

• The key for series should only appear when there is a series in the job family list that is defined as mission critical.

Usability

When to use

• Appears between the "Duties" and "Requirements" sections of the job announcement.

Guidelines

• The job title opens the JOA in a new tab.
• The "Who may apply" link opens the JOA in a new tab and anchors to the Who May Apply section within the JOA.
• The level one agency should be the agency listed.
• The date should be in the format MM/DD/YYYY.

Usability

When to use

• After a user has selected a job listing the JOA Summary should be present as they learn more or apply for the job.

Accessibility

• Modal should have the role="dialog" attribute.
• Content behind the modal should not scroll while the modal is open.
• Modal should have an aria-labelledby attribute where the value is the ID of the modal title (you don't need or want the #).
• Modal should have an aria-describedby attribute where the value is the ID of a div that contains a description of the modal (you don't need or want the #).
• Pressing the ESC key should close the modal and return the focus to the element that triggered the modal.
• If the modal contains a form, pressing the Enter key should submit that form.

Usability

When to use

• When the focus on the user must be focused on a single, or limited number, of elements. For example, when confirming or canceling a required action.
• The flow the user is in would otherwise be interrupted by a distinct page.

Do not use when

• Content that must be linkable (have a distinct URL) or searchable.
• The contents of the modal is a form longer than 4 fields.

Guidelines

• Retain form input: All data entered into a modal should be retained until the modal is submitted. Thus if a user enters data, dismisses the modal, and then reopens the modal the form data should be populated in the form fields.

Usability

When to use

• When an action is required by the user before they may continue.
• When it is necessary to redirect the user to another part of the site.

Guidelines

• These modals are simply containers for an alert. Thus the modal should adhere to the guidelines for the appropriate alert.
• Modals that manage destructive actions should be triggered by a red, secondary button and should use the error alert style. However, unlike the deafult error alert these modals should allow the user to dismiss them.</a>

Accessibility

• Unfortunately, we have a number of these modals and we should excise them as quickly as possible. Content behind these modal has to scroll to support the egregious form lengths on mobile devices.

Usability

When to use

• Never. Long forms do not belong in modals.

Guidelines

• Do not create new instances of modals that contain long forms.
• Retain form input: All data entered into a modal should be retained until the modal is submitted. Thus if a user enters data, dismisses the modal, and then reopens the modal the form data should be populated in the form fields.

Usability

When to use

• Use when the Account name (Profile v3 variation) or Help (Help v3 variation) are selected in the top navigation, respectively. Use the Profile v3 for Open Opps users variation when a user is in an Open Opps session.
• Both variations should be fixed to the top of the viewport as the user scrolls.
• The Open Opps variation should navigate the user back to their Open Opps profile or, failing that, https://openopps.usajobs.gov/home

When NOT to use

• Do not use this specific variation outside of Account and Help.

Guidelines

• Do not use icons alongside nor within the text of the navigation labels
• Do not use the required asterisk alongside nor within the text of the navigation labels. Please do use the form legend component to indicate that the entire section is required.

Usability

When to use

• Use secondary navigation to allow the user to move laterally to other sub-sections of a section. For example, to move between sub-sections of their Profile.

When NOT to use

• Avoid using this component to move within the same page. Typography, including clear section headers, should be enough to allow the user to navigate the page.

Accessibility

• Ensure the navigation system is keyboard accessible. Users should be able to tab through each link.
• Ensure the header which wraps the entire nav has the role set to "banner" and the nav must have a role set to "navigation". Refer to the W3C ARIA landmarks documentation.
• Ensure that the Account and Search menu toggles have the aria-controls attribute set to the ID name of the container which uses the aria-expanded attribute set to false when hidden and true when expanded.

Usability

When to use

• This variation is full bleed and conforms to the larger 1600px site wide max width. It also shows help at narrow view ports.

Implementation

• The user's first and last initials are used at the narrowest viewport widths. At the M breakpoint (600px) the full first name of the user is shown.
• Padding should be applied to the anchor element (a) to increase the tappable target size. The padding should also reach to the top and bottom of the navigation element.
• Padding around the first element (logo) should reach to the left edge of the page to enlarge the tappable target.
• Padding around the last element (Search) should reach to the right edge of the page to enlarge the tappable target.
• As the user types into the location field an auto-complete box should appear below the input field suggesting locations that match a known list of locations. API for locations.
• As the user types into the keyword field an auto-complete box should appear below the input field suggesting job titles, occupations, agencies & departments, and series that match known lists of those items.
• The active state for search is a distinct treatment as it opens the search drawer that contains the search form.

Usability

When to use

• Use this variation when the user is authenticated via login.gov.
• NOTE: This variation is depicting secondary navigation as well for when the user is on their home, profile, documents, or preferences pages.

Accessibility

• When the banner is in focus it should be dismissible via the keyboard.

Usability

When to use

• Use the unauthenticated banner variation to explain to users our move to login.gov.

Usability

When to use

• Use this variation for the Open Opportunities application.

Usability

When to use

• Use this variation for the Open Opportunities application.

Usability

When to use

• Use the Logo-only variation when the user should be prevented from navigating away from the current page. Examples inlcude the sign-in and create account pages.

Usability

When to use

• Use this variation in the test and UAT environments to make clear to any user of those systems that this is not the production system.

Usability

When to use

• For use in the Agency Talent Portal product.

Usability

When to use

• Use pills when you need to indicate the state of an object/component

When to consider something else

• Do not use pills for non-state or status.

Usability

When to use

• Use this variation of pill for indicating the state of a search or transaction (transient state).
• The green variation here represents a value that came from the user's profile preferences. The gray variation is a value matches the value of a filter that the user has applied to their search results.

When to consider something else

• Do not use pills for non-state or status.

Usability

When to use

• Use a progress indicator when you need the user to complete several steps in a process.

When to consider something else

• Do not use this progress indicator for a process with less than 3 steps.

Usability

When to use

• Use this variation in the application guide process in conjunction with the JOA summary component.

Usability

When to use

• Use this progress indicator when the number of steps is small (less than 3 ideally) and there is not a need for the user to go back.

When to consider something else

• Do not use this progress indicator for a process with more than 3 steps.

Usability

When to use

• Use the step indicators when you want to highlight steps but don't need a full progress indicator in the current context. For example, these step indicators are used in new user onboarding when showing an initial summary of the steps the user will go through on subsequent pages.

When to consider something else

• Do not use step indicators for other numbering contexts. An ordered list will suffice in most instances.
• Do not use step indicators instead of one of the progress indicators above.

Implementation

• The steps utilize an ordered list to stick to semantic UI standards.

Usability

When to use

• Use this pattern to show the next N in a list where N is 10 to 25 items in a list. This is a simplistic pagination pattern.

When to use something else

• Do not use this pattern for more rigorous pagination needs such as search results.

Implementation

• The trigger button should be pushed down by page by the content it reveals.
• If there are not N more items to show, where N is 10 or 25, then the trigger button does not appear as there are no more items to reveal.
• The browser should scroll down to the first item in the list.

Usability

When to use

• Use this pattern to allow the visibility of the content to be toggled.

Implementation

• The browser should scroll down to the first item in the list.

Usability

When to use

• Use this pattern to show some of the content and indicate to the user that there is more content to be revealed.

Implementation

• Depends upon Readmore.js.

Usability

When to use

• When the number of results are relevant to explain to the user the relative success of their query.

When not to use

• When there are no results (see "No results found").

Guidelines

• Do not show search controls or pagination when no results are displayed.

Usability

When to use

• When zero results are returned by the user's query.

Accessibility

• The previous and next buttons are hidden with aria-hidden when they are non-functional.

Implementation

• Below the M breakpoint (600px) the pagination is represented by the next and/or previous buttons.
• Above the M breakpoint there are several rules:
  • The first and last page links are always displayed.
  • Current page number is always displayed with +/- 1 page to either side.
  • When displaying the first and last pages +/- 2 pages are displayed.
  • When displaying the first page the Previous button is not displayed.
  • When displaying the last page the Next button is not displayed.
  • There are only ever 5 page links displayed, including first and last page. All other pages are abbreviated into ellipses.
• Pagination should always be shown at the bottom of the page, near the bottom of the list that it paginates.

Usability

When to use

• When it is not feasible to show all ordered data on a single page.

Do not use when

• When it is undesirable to have the user pause for navigation. Some alternatives include the infinite scroll pattern or simple un-numbered navigation.

Requirements

The search card component MUST include the following:

• Position title
  • display position title as a link that opens the job posting (job announcement) in the same window.
  • on click, change the link to visit link state (purple link).
    • MUST remain in this state for the entire session.
    • MUST remain in this state even when the user signs out and signs back in.
• Agency name
• Department name
• Location
• Starting salary & matching starting-ending pay schedule (example: GS13-14)
• Appointment type (formerly known as work type)
• Work schedule
• Hiring paths icons
• The label/description is shown on the hover state
• Opening and closing period
• Save/saved star trigger
  • Only show to signed-in users
  • Display as a link that will allow users to save and un-save a job posting.
  • Follow the save/saved star trigger guidelines.
  • Do NOT display the save/saved star trigger to signed-out users.

The search card component MAY include the following:

• Application status: If the user has a started or finished an application to this job then the application status should appear. The same state names and colors as appear for application status in the profile dashboard should be employed.

When to use

• To represent a job announcement in a list of announcements.

When to use

• To represent a job announcement an a Mission Critical Occupation page.
• THIS VARIATION IS TO BE REPLACED BY THE STANDARD CORE VARIATION ABOVE.

When to use

• To represent a job announcement in the recruitment tool.

When to use

• To represent an opportunity in Open Opportunitites.

Guidelines

• The teaser, when it appears, should appear between the 5th and 6th job result. Ideally it would be loaded via an asynchronous request after results are displayed so that it does not negatively impact search performance.
• Only one teaser should be shown in one set of search results. Currently there is overlap in triggering keywords thus a round robin mechanism should be deployed to rotate between the overlapping teasers. There is also the possibility of overlap in the use of filters. In this case the keyword trigger should win out.
• Links that leave the usajobs.gov domain should open in a new tab.

When to use

• Each teaser appears in search results IF and only if they are relevant to the search. Relevance is defined by keyword for these variants excluding the Event variation which is dependent upon location and/or hiring path.
• Events:
  1. Location: A matching event should appear when the location entered into the Location search field and selected from autocomplete matches the location of the event.
  2. Future enhancement - Hiring path: A matching event should appear when the hiring path filter selected matches one or more of the hiring paths attached to an event.

When teasers appear

• Teasers should appear as long as the criteria below are met. Their appearance is not based on a session given that these are not currently popular queries.
• Keywords: When the user enters this string into the keyword field the appropriate teaser should appear in their search results.
• Occupations: When the user enters this string into the keyword field AND selects the matching occupation from autocomplete the appropriate teaser should appear in their search results.
• Department/Agency: When the user enters this string into the keyword field AND selects the matching department or agency from autocomplete the appropriate teaser should appear in their search results.