[Hiring] Website Mobile Readability Reviewer @HRS Talent Solutions

Role Description

A visitor using a phone should be able to read the same essential information as someone at a desk. This remote job checks assigned online pages at mobile screen widths and records visible problems for the website team. It uses the precision of office administration and supports customer service when a form, button or instruction becomes hard to use. You will describe what you see and retest an approved fix; you will not write CSS or choose a new design independently.

Remote | Part-time | $28.25 - $30.45 per hour

A quiet home office with access to a computer and a phone-sized view is useful for repeated comparisons.

• Describe what a reader sees:
• A heading may wrap over a button, or a table may require awkward horizontal scrolling.
• Open the assigned page at the specified device width and record the exact problem, location, and test conditions.
• Do not label a page “broken” without a reproducible observation.
• If the page has private customer information in a test environment, keep screenshots within the employer's approved tool.
• A temporary browser zoom setting can change the result, so follow the supplied setup consistently.
• You may be asked to check a correction:
• Use the same steps and compare the new view with the earlier report.
• If a fix solves one problem but creates another, record both without altering the code.
• Office administration matters because the developer needs a clear URL and screenshot; customer service awareness matters because a visitor may leave when a form button cannot be seen.
• Report a reader’s experience, not a guess about the code:
• A table may require sideways scrolling, a heading may cover a button, or a paragraph may appear in a narrow column.
• Identify the page, screen size and exact area, then describe the problem in terms another person can reproduce.
• If a page is merely unfamiliar to you, compare it with the supplied checklist before reporting a defect.
• Once the owner says a correction is ready, reopen the live page at the same width and check the affected area again.
• A saved change is not proof that the customer-facing page has improved.
• Work you may do:
• Open assigned online pages in specified mobile views.
• Check text, buttons, forms, and simple navigation against a guide.
• Record the page, device width, and visible issue.
• Keep test screenshots in the approved system.
• Refer design and code changes to the website owner.
• Retest an authorized fix with the same steps.
• Mark unresolved items accurately in the tracker.
• Previous website experience is helpful but not required:
• Customer service or office administration background can also transfer.
• The employer will train beginners on its test views and reporting method.
• You should be observant and able to describe a problem without guessing its cause.
• A page may have a sticky header that hides a form field on a small screen or a table that cannot be read without scrolling sideways:
• Use the checklist's device sizes and note how far you scrolled before the problem appeared.
• If a page works only after rotating a phone, record that observation rather than deciding whether it meets a design standard.
• The website owner will make that judgment.
• Some issues are caused by a particular browser or an enlarged text setting:
• Record those conditions so the team can reproduce the problem.
• Avoid switching between views mid-test without noting it.
• A screenshot should show enough context to identify the page, while keeping any test-account details out of a general report.
• If the site team changes the page, repeat the relevant steps and state what improved and what remains difficult.
• A precise description supports a practical fix and prevents the same issue from being reported as several unrelated bugs.
• If a customer has already reported difficulty using a page:
• Keep their original description linked to the test item.
• The website team may want to know whether the observed issue matches what the person experienced.
• Do not promise a fix date in a public support reply.
• You can confirm that the report was recorded and routed, while the owner makes decisions about the change.

Qualifications

• Web development experience is not required.
• You should be able to follow a visual checklist, take clear notes and explain where an online page is difficult to use.

Requirements

• If you’re selected for the next step, you may be asked to complete an application on the hiring company’s website.
• If your resume includes any content review, office administration or customer service work, include it as transferable experience.