10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Ophélie David

Ophélie David

Accessibility program manager in digital publishing

Full-depth AI personas

Why this persona fits the audience

She manages the accessibility review queue for a publishing house and checks whether exported PDFs meet internal requirements before release and archive. Her team works with editorial Markdown, tagged layouts, and document QA checklists for every quarterly publication cycle.

  • Age: 36
  • Location: Paris, France
  • Occupation: Accessibility program manager
  • Income: €64,000
  • Education: Master's in Information Science
  • Company size: mid-sized publishing house (150 employees)
  • Years in role: 5
“‘I don’t just fix PDFs—I fix the fact that someone, somewhere, will have to read these files in 50 years. And they should have the same access as everyone else.’”

Ophélie David grew up in the 7th arrondissement of Paris, the daughter of a schoolteacher and a municipal librarian. Her father’s obsession with MARC cataloging standards was her first exposure to the idea that information systems should serve all users, a philosophy she carried into her degree in Information Science. After working as a metadata specialist for a small press, she landed her current role five years ago, where she quickly became the de facto authority on PDF accessibility. Her team’s QA process is now a case study in her employer’s training manuals, though she bristles at the praise—‘It’s not a choice,’ she’ll say. ‘It’s the law, and it’s the right thing to do.’ Her pet peeve is the myth that accessibility is expensive or slow; her team’s checklists save the company far more in lawsuit-prevention costs than they cost to maintain. Lately, she’s been pushing to adopt more automated tools to handle the 20% of files that consistently fail compliance, but her IT department’s reluctance to integrate new APIs has stalled progress. Her long-term goal is to transition from triage to prevention, embedding accessibility checks earlier in the editorial pipeline. When she’s not at work, you’ll find her either at a café in Montmartre with a stack of industry reports or at home, meticulously repairing a 1920s typewriter—the ‘manual version of the work we do,’ she jokes. Ophélie’s life is a quiet rebellion against hurry, a one-woman crusade to prolong the shelf life (digital or otherwise) of well-made documents.

Background & daily life

A day in their life

Ophélie’s weekday starts at 7 AM with a cup of roasted chicory (she swore off coffee in 2021) and a quick scan of her team’s Slack channel. By 8:30, she’s at her desk, reviewing a backlog of 18 pending PDFs—three of which are already past their deadlines. ‘Bon, again,’ she sighs, pulling up a sample to check for proper heading hierarchy. Her 10 AM stands with the design team descends into a debate about why ‘decorative’ images still need alt text. ‘If it’s decorative, you shouldn’t have put it there,’ she fires back. The afternoon is a blur of fixing unescaped Markdown and drafting an email to IT about their slow server response times. At 6, she locks her laptop with a satisfied click—only to grab it again to troubleshoot a last-minute ticket about a missing language tag. ‘Tomorrow,’ she sighs, ‘is another day.’

Lifestyle

Ophélie lives in a quiet, book-lined apartment in the 11th arrondissement, where she spends weekends reading (mostly nonfiction) or walking along the Seine with her aged but energetic Border Terrier, Oiseau. She’s frugal by nature—she budgets meticulously for annual trips to Lyon to visit her elderly mother and occasional typography workshops. Health-wise, she prioritizes long walks and skips coffee (a deliberate choice after a caffeine-induced anxiety episode years ago). Socially, she’s part of a small, tight-knit group of publishing professionals who meet monthly for informal discussions about industry challenges. She avoids large gatherings, preferring deep, one-on-one conversations.

Work life

Ophélie’s workdays begin with a morning ritual of reviewing overnight accessibility alerts from her team’s shared dashboard. She spends 40% of her time auditing PDFs, another 30% refining internal checklists, and the rest in cross-departmental meetings where she often has to translate technical standards into actionable steps for designers. Her team of three is lean but effective, using a mix of open-source tools and in-house scripts to streamline workflows. The biggest friction? Persuading editorial teams to test early—‘We can’t fix unstructured Markdown after the fact,’ she mutters under her breath at least twice a week. Her manager respects her expertise but nibbles at her budget for new tools, leaving her to justify every €100 spent.

Relationships

Ophélie’s closest relationships are with her college friends—now scattered across Europe—and her 72-year-old mother, who still calls her ‘ma petite administrateur’ despite her professional success. She’s the go-to problem-solver in her group of publishing colleagues, the one people text at 10 PM with emergency questions. She admires her boss’s strategic vision but privately worries he undervalues the legal risks of non-compliant exports. Her late father, a librarian, instilled her love of well-structured information systems; she still flips through his old cataloging manuals for inspiration.

How they decide

Methodical and data-backed, but with a pragmatic bent. She’ll prototype small changes before scaling, and her team knows she’ll test a tool for three months before endorsing it. She’s wary of vendor claims but deeply values peer testimonials from trusted colleagues in the field. Her hesitation isn’t about cost as much as about whether the tool will outlast her current crisis—‘We don’t need another thing to patch; we need a thing that lasts,’ she’ll say.

How they sound

Ophélie speaks in measured, deliberate sentences with occasional wry asides dropped into her native French. She’s formal in meetings but leans into sardonic humor in private. Phrases like ‘non, mais’ and ‘je vous assure’ pepper her speech, and she rolls her eyes at vague language—’What does “mostly accessible” even mean?’ she’ll ask at team meetings. She avoids corporate jargon unless mocking it (‘synergy’ makes her laugh in a way that’s not quite polite). Her voice is warm but guarded, and she rarely raises it, even when frustrated.

Personality traits

  • methodical but not rigid—revises processes without overhauling them
  • quietly persistent in advocating for accessibility standards
  • hates rushing but is frustrated by colleagues who treat PDF accessibility as an afterthought
  • collects vintage typewriters as a hobbyist
  • strict about separating work and leisure time
  • prides herself on remembering minor but consequential details in documents
  • skeptical of trendy tech solutions without proven compliance records
  • prefers email over calls for clarity (and to avoid interruptions)
  • occasionally sarcastic in team meetings, but only privately
  • loyal to brands that align with her values

Goals

  • Promote Ophélie to lead the new accessibility standards committee at the company
  • Publish a white paper on integrating WCAG 3.0 into legacy publishing pipelines
  • Spend a month in a Swiss bookbindery to study analog archival techniques (a longheld dream)
  • Train a junior team member to take over her QA checklist maintenance workflow
  • Reduce screen time by 30% (currently fails at this daily, but keeps trying)

Problems & frictions

  • Her workflow is stitched together from outdated legacy systems and manual hacks
  • Colleagues treat her team as ‘the PDF police’ and file tickets at the last minute
  • The company’s PDF export templates haven’t been updated in two years, creating recurring compliance risks
  • Her team’s script for batch accessibility checks crashes when handling large files
  • She’s tired of explaining why ‘just getting it done’ isn’t good enough for archives

Values

  • inclusion
  • accuracy
  • standards
  • public quality
  • collaboration

Interests

  • WCAG
  • digital publishing
  • reading
  • document QA
  • typography
  • urban hiking

Media habits

  • listens to podcasts on accessibility standards during commutes
  • reads industry blogs like *Accessibility Matters*
  • watches YouTube tutorials on PDF tools
  • avoids social media beyond LinkedIn for professional networking

Questions & answers

Ophélie David’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying makesPDF (https://makespdf.com) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The main thing stopping me from trying makesPDF this month is the uncertainty about integrating it with our existing workflow. My team already uses a mix of open-source tools and in-house scripts, and adding a new tool would require thorough testing to ensure it aligns with our compliance needs. Additionally, I need to understand how it handles unstructured Markdown and whether it can seamlessly fit into our editorial pipeline. Currently, we manually audit PDFs for accessibility, and while the promise of automated compliance is appealing, I’d need to verify it thoroughly before committing. The mention of a free tier with 10 credits per month is intriguing, but I’m not sure how that translates to our volume of documents. I’d also want to know if their API can handle our peak loads without bottlenecks. As for budget, I’d consider up to $100 per month if it proves to be reliable and time-saving, but only after a trial to confirm it passes our internal standards.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.